Add ALGORITHM and LOCK support for MySQL ALTER TABLE operations #955
+503
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds support for MySQL's
ALGORITHMandLOCKclauses inALTER TABLEoperations, enabling zero-downtime schema migrations for compatible operations on MySQL 8.0+ and MariaDB 10.3+.Why This Is Useful
Production Impact:
ALGORITHM=INSTANTallows adding nullable columns, dropping columns, and other compatible operations without copying the entire tableLOCK=NONEto ensure migrations don't block concurrent reads/writesReal-world scenario:
Implementation
Class Constants (No Magic Strings)
Key Features
Important MySQL Restriction
LOCK=NONE,LOCK=SHARED,LOCK=EXCLUSIVE) due to MySQL limitations. Use either:ALGORITHM=INSTANTalone (recommended)ALGORITHM=INSTANTwithLOCK=DEFAULTALGORITHM=INPLACEwith any LOCK optionUsage Examples
Single operation:
Batched operations:
Changes
algorithmandlockproperties with getters/settersCompatibility